Week one of a new job comes with a quiet instinct: keep your head down, absorb everything, speak once you understand the place. Follow that instinct and you will still be the slowest person in the room in month four. The people who get up to speed fast do something that feels reckless at the start.
Compute the coefficients of the arc tangent series by Thursday
Grace Hopper reported to the Bureau of Ordnance Computation Project at Harvard on July 2, 1944. She was a Vassar mathematics professor with no computing experience whatsoever. Commander Howard Aiken greeted her by asking where the hell she had been, waved at a machine filling the room, and told her it was a computing machine. Then he asked her to compute the coefficients of the arc tangent series by Thursday. Hopper's own account of that morning describes her practically cowering while she said yes.
What she had to work with was a book of instruction codes scribbled down by the programmer before her after his test runs. This made her the third person ever to program the Harvard Mark I, working from someone else's handwriting with four days on the clock. She delivered.
The thing she did next is the actual lesson
Hopper took on the job of documenting the machine. The result was the 561-page manual of operation for the Mark I, which she wrote while she was still the least experienced person on the project. Writing it forced her to hunt down every gap in her own understanding, because a gap you can skip while reading becomes a hole you cannot skip while explaining.
Cognitive science backs the sequence. A 2014 study by Nestojko, Bui, Kornell, and Bjork in Memory and Cognition gave two groups the same passage. One group expected a test. The other expected to teach it to another student. Nobody actually taught anything, and everybody got tested. The group expecting to teach recalled more, organized it better, and held onto the main points more tightly. Changing only the expectation changed how the material got encoded.
Absorbing material produces recognition, which feels like learning and collapses the moment somebody asks you a follow-up question. Preparing to explain it produces knowledge you can use under pressure. Build your first three weeks around explaining.
Week one: map the place, do not try to master it
Your only deliverable this week is a document nobody asked for. Three sections.
- Names and jobs. Every person you meet, what they own, and what they come to you for. Include the person in finance who unblocks purchase orders.
- The glossary. Every acronym and internal term you hear, with a plain definition you confirmed with someone. Aim for thirty entries by Friday.
- Triage list. Split what you do not know into "need now," "need soon," and "good to know later." Systems access sits in the first bucket. Quarterly strategy sits in the third. Sorting alone kills half the overwhelm.
Ask your manager one question on day two: "What should I be able to do without help by the end of month one?" That answer sets your target.
Week two: rebuild last month's work and count the gaps
Find one process you will own. Pull last month's finished version, then rebuild it yourself from scratch without looking at the answer until you are done. Compare line by line.
Every difference is a question with a name attached, which beats "can someone walk me through this" by a wide margin. When you ask why a step exists and the answer comes back as tradition, you have found something worth noting. The phrase "we've always done it that way" was, in Hopper's judgment, the most dangerous one in the language, and she reached that conclusion as the person who had walked in knowing nothing.
The question format senior people actually answer
Two rules keep you from burning goodwill.
First, never ask a question you have not attacked for ten minutes yourself. Second, never ask the same question twice, which means you keep an answers file and search it before you open your mouth.
Then use this format, which turns a request into a two-second correction:
"My read is that we exclude refunded orders from the weekly number because they double-count in the finance sheet. Where does that break?"
Batch these. Three or four per message beats four separate interruptions, and it lets someone answer while their coffee cools.
Week three: write the document that does not exist
By now you have a glossary, a rebuilt process, and a pile of corrected assumptions. Turn it into one short guide for the next person hired into your seat. Two pages. How the process runs, what breaks it, and who to ask when it does.
Send it to your manager with one line: "Here is how I understand this. Tell me where this is wrong."
Three things happen at once. Every soft spot in your understanding surfaces, because you cannot fake your way through writing steps down. Your manager gets to correct you cheaply, in writing, before an error reaches a customer. And a person who has been on the team for twenty days has handed the team an asset. Hopper walked in as the least qualified person in that laboratory and left with her name on the manual everyone else used.
Do this before you log off Friday
Send your manager one message with a ranked list: the three things you believe you were hired to fix, in the order you think they matter. Then ask them to reorder it.
"Based on my first weeks, here is what I think I am here to fix, ranked. 1. [X] 2. [Y] 3. [Z]. Would you reorder this list? Getting the order right matters more to me than being right."
Six months of quiet guesswork about what actually matters is the standard experience for a new hire. One message on a Friday afternoon buys you the answer outright, and it tells your manager you care about hitting the right target more than looking clever.
Until next time, future leader.
